home *** CD-ROM | disk | FTP | other *** search
- Path: tank.news.pipex.net!pipex!demon!centa.demon.co.uk
- From: pjt@centa.demon.co.uk (Paul Toland)
- Newsgroups: comp.lang.c++,comp.os.ms-windows.nt.misc,comp.os.ms-windows.programmer.tools.mfc,comp.os.ms-windows.programmer.win32
- Subject: MFC Extension DLL creation - different in VC++4?
- Date: Mon, 29 Jan 1996 13:40:48 GMT
- Organization: Cursa Systems Ltd
- Message-ID: <822894063.29249@centa.demon.co.uk>
- NNTP-Posting-Host: centa.demon.co.uk
- X-NNTP-Posting-Host: centa.demon.co.uk
- X-Newsreader: Forte Free Agent 1.0.82
-
- Using Microsoft Visual C++ V4.00 on NT3.51
-
- I Created a simple project with a single App Wizard generated
- Dialog based MFC EXE, and a single App Wizard generated
- MFC Extension DLL as a sub-project of the EXE.
-
- The DLL had a dialog defined in it, with a Class Wizard generated
- class. An instance of this dialog was created in the EXE:
- CNoddyDialog dlg;
- dlg.DoModal();
-
- This resulted in no Dialog, and an Access violation exception,
- as the dialog template resource could not be found. Similar results
- where found with String resources in the DLL.
-
- The V4.00 App Wizard seems to generate a totally different type of
- 'DLL', defined as CWinApp, which does not appear in the main App's DLL
-
- list (as can be seen using DLLHusk example code) and hence is not
- searched for resources.
-
- If the DLL is defined using the 'old' method with 'C' type DllMain
- and InitDLL routines, then it works as before.
-
-
- How do I expose my DLL resource using the the new App Wizard?
-
-
-
-
-
-
-
-
-